Dynamic provisioning of a firewall role to user devices

ABSTRACT

A system and method of providing security service to a mobile traffic network are provided. A local network group comprising a plurality of user devices that are subscribed to the security service is created. One of the plurality of the user devices is selected to act as a firewall for the plurality of user devices of the local network group. The selected user device is provisioned to act as a firewall for the local network group. A message is sent to the plurally of user devices of the local network group to route communication through the selected user device via a short range wireless communication technology.

BACKGROUND

In recent years, wireless communications have become increasinglypopular. Mobile devices are used to make voice calls, check email andtext messages, update social media pages, stream media, browse websites,and so forth. In addition, the internet of things (IoT) may include anetwork of user devices, vehicles, buildings, etc., that have embeddedtherein various electronics, software, sensors, actuators, and networkconnectivity that enable these devices, collectively referred to hereinas user devices, to collect and exchange data via wirelesscommunication. As more communication user devices and applications havemigrated to packet transport that was often intended for an openInternet application, they have become subject to many of the securityissues that plague the public Internet. Malicious activity, such asBotnet, distributed denial of service (DDOS), Malware, and the like, isbecoming of increasing concern. As the number of user devices that cancommunicate over the mobile communication network increases, networkoperators attempt to find new ways of providing network security withoutsubstantial investment in additional hardware.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures, in which the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 illustrates an example architecture for implementing a dynamicprovisioning of a firewall role to a user device.

FIG. 2 is a block diagram showing various components of an illustrativeuser device.

FIG. 3 illustrates an example scenario where an embodiment of a dynamicprovisioning of a firewall role is used.

FIG. 4 presents an illustrative process for dynamically provisioning afirewall function to a user device.

FIG. 5 provides a functional block diagram illustration of a computerhardware platform that may be used to implement a dynamic provisioningof a firewall role to a user device.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth by way of examples in order to provide a thorough understanding ofthe relevant teachings. However, it should be apparent to those skilledin the art that the present teachings may be practiced without suchdetails. In other instances, well known methods, procedures, components,and/or circuitry have been described at a relatively high-level, withoutdetail, in order to avoid unnecessarily obscuring aspects of the presentteachings.

This disclosure generally relates to wireless networks, and moreparticularly, to optimizing wireless networks by dynamically assigningnetwork roles to user devices. A central server creates a local networkgroup comprising a plurally of user devices. One of the plurally of theuser devices is selected to act as a firewall for the user devices ofthe local network group. The selected user device is provisioned by thecentral server to act as a firewall for the local network group. Theuser devices of the local network group route communication through theselected user device via a short range wireless communicationtechnology, which may provide additional security to the user devices inthe local network group, reduce the probability of dropped calls,disburden the mobile traffic network, and reduce power consumption onthe user devices. The techniques described herein may be implemented ina number of ways. Example implementations are provided below withreference to the following figures.

Example Network Architecture

FIG. 1 illustrates an example architecture for implementing a wirelessnetwork optimization system configured to provide a dynamic provisioningof a firewall role to a user device. FIG. 1 illustrates a mobilecommunication network 100 as may be operated by a mobile communicationnetwork carrier or service provider to provide a wide range of mobilecommunication services and ancillary services or features to itssubscriber customers and associated mobile device users. Many of theelements generally indicated by the reference numeral 100 are elementsof the motile communication network and are operated by or on behalf ofthe carrier. The mobile communication network 100 providescommunications between various user devices (user devices), such as userdevices 102(1) to 102(n), as well as communications for the UDs withnetworks and stations outside the mobile communication network 100.

For purposes of later discussion, several user devices appear in thedrawing, to represent some examples of the devices that may receivevarious services via the mobile traffic network 120. Today, user devicestypically take the form of portable handsets, smart-phones, tabletcomputers, personal digital assistants (PDAs), and smart watches,although they may be implemented in other form factors, includingconsumer, sensor, and business electronic devices, sometimes referred toas IoT's.

The mobile communication network 100 provides communication for userdevices 102(1) to 102(n), as well as for mobile devices that do notparticipate in the dynamic provisioning of a firewall role describedherein. Mobile communication network 100 allows users of the userdevices (e.g., customers or subscribers to the mobile traffic network120) to initiate communication, and receive information from the packetdata communication network (PDCN) 124.

The mobile communication network 100 typically is implemented by anumber of interconnected networks. Hence, the overall mobilecommunication network 100 may include a number of Mobile trafficnetworks (RANs) 120, as well as regional ground networks interconnectinga number of RANs and a wide area network (WAN) interconnecting theregional ground networks to core network elements, such as theMultimedia Messaging Service Centers (MMSCs). A regional portion of themobile communication network 100, such as that serving user devices102(1) to 102(n) may include one or more RANs (represented by the mobiletraffic network 120) and a regional circuit and/or packet switchednetwork and associated signaling network facilities.

Physical elements of a mobile traffic network 120, operated by one ofthe mobile service providers or carriers, include a number of basestations, represented in the example of FIG. 1 by eNodeB 104(1) and104(n) nodes. Such eNodeB 104(1) to 104(n) nodes may include a basetransceiver system (BTS) that communicates via an antennae system at thesite of the node and over the air-link with one or more of the userdevices (102(1) to 102(n)) when the user devices are within range. EacheNodeB 104 node may include a BTS coupled to several antennae mounted ona radio tower within a coverage area (e.g., within a predetermined rangeof a geolocation) often referred to as a “cell.” The BTS is the part ofthe radio network that sends and receives RF signals to/from the userdevices that the eNodeB node 104 currently serves.

The mobile traffic network 120 carries the user communications for theuser devices between the respective eNodeB 104 nodes and other elementswith or through which the user devices communicate. Some individualelements such as switches and/or routers forming the mobile trafficnetwork 120 are omitted here for simplicity. It will be understood thatthe various network elements can communicate with each other, as well asother elements of the mobile traffic network 120, and other networks(e.g., the public switched telephone network (not shown) and theInternet 128) either directly or indirectly.

By way of illustrative example only and not limitation, the mobiletraffic network 120 includes elements of the Evolved Packet Core (EPC)and the Evolved Universal Mobile Telecommunications System (UMTS)Terrestrial Access Network (E-UTRAN) and the access network E-UTRAN. Forsimplicity, classical UMTS architecture elements, such as the UTRAN, arenot displayed, while it will be understood that such architectures aresupported as well by the teachings herein.

The Mobility Management Entity (MME) 106 is the control node thatprocesses the signaling between the user devices 102(1) to 102(n) andthe mobile traffic network 120. The Home Subscriber Server (HSS) 108includes the user device users' subscription data, such as the EvolvedPacket System (EPS) subscribed quality of service (QOS) profile andaccess restrictions for roaming.

The serving gateway (S-GW) serves as the local mobility anchor for databearers when a user device moves between eNodeB's (e.g., from eNodeB104(1) to 104(n)). It also retains the information about the bearerswhen the UE is in the idle state and may temporarily buffer downlinkdata while the MME 106 initiates paging of the user device toreestablish the bearers. In addition, the S-GW performs someadministrative functions in the mobile traffic network 120 such ascollecting information for charging against an account of a UD. Forexample, the volume of data routed to or from a user device (e.g.,102(4)) over a user device (e.g., 102(3)) that is provisioned to operateas a firewall may be calculated, such that an account of the firewallprovisioned user device (e.g., 102(3)) is not charged for thecommunication for one or more other the user devices (e.g., 102(4) to102(7)). The provisioning of a user device to perform the functions of afirewall is discussed in more detail later. The MME 106 also may serveas the mobility anchor for interworking with other 3GPP technologiessuch as general packet radio service (GPRS) and UMTS.

The Packet Data Network Gateway (P-GW) 112 is responsible for IP addressallocation for the UD, as well as QoS enforcement and flow-basedcharging according to rules from the policy charging rules function(PERF) 114. It may filter the downlink user IP packets into thedifferent QoS-based bearers. This is performed based on Traffic FlowTemplates (TFTs). The P-GW performs QoS enforcement for guaranteed datarate (GBR) bearers. It should be noted that while a single gateway 112is illustrated in FIG. 1 for simplicity, different types of gatewayservers may be used for different wireless technologies. For example, ahigh availability (HA) server can be used for 3G; a P-GW server for 4G;general packet radio service core network (GGSN) for 2G, 3G, andwideband code division multiple access (WCDMA); etc. The different typesof gateway servers are sometimes collectively referred to herein asgateway server 112.

The Policy Control and Charging Rules Function (PCRF) 114 is responsiblefor policy control decision-making, as well as for controlling theflow-based charging functionalities in the Policy Control EnforcementFunction (PCEF), which is in the P-GW 112.

The service provider of the mobile traffic network 120 may also operatea number of systems that provide ancillary functions in support of thecommunications services and/or application services provided through themobile traffic network 120, and those elements communicate with othernodes or elements of the mobile traffic network 120, such as one or moreprivate IP type packet data networks based on a packet datacommunication network (PDCN) 124, sometimes referred to as an Intranet(i.e., a private network). Generally, such systems are part of, orconnected for, communication via the PDCN 124 and may provide additionalservices such as providing a dynamic provisioning of firewall roles touser devices 102(1) to 102(n) over the mobile traffic network 120.

In the example of FIG. 1, there is a central server 130 that isconfigured to communicate with the user devices 102(1) to 102(n) via thePDCN 124 and the mobile traffic network 120. The central server 130 canalso communicate over the Internet 128. In one embodiment, the centralserver 130 has a security engine 140 (e.g., a software program stored inits memory) to perform various control functions. In variousembodiments, the functions of the security engine 140 may includedetermining what user devices (e.g., 102(1) to 102(n)) can communicatevia a wireless local area network (WLAN), a wireless personal areanetwork (WPAN), or a wireless sensor actor network (WSAN), collectivelyreferred to herein as short range wireless communication technology. Forexample, user devices 102(3) to 102(7) may communicate with each other,without limitation, over Digital Enhanced Cordless Telecommunications(DECT), Near Field Communication (NFC), ZigBee, Bluetooth,ultra-wideband (UWB), wireless USB, or the like. One advantage of usingshort range wireless communication technology is that it typically usesless power than direct communication with a base station (e.g., 104(N)).

The security engine 140 of the central server 130 may create a localnetwork group 150 based on the user devices that are within the scope ofshort range wireless communication of each other. For example, upon thesecurity engine 140 determining that user devices 102(3) to 102(7) cancommunicate with each other over a short range wireless communicationtechnology, the security engine may regard these user devices 102(3) to102(7) as a local network group 150 that may be used to enhance and/ormake more secure the communication services provided over the mobiletraffic network 120. To that end, the security engine 140 may select oneof the plurality of user devices 102(3) to 102(7) to act as a firewallfor the remaining user devices. For example, user device 102(3) may beprovisioned by the security engine 140 to be used as a firewall. Putdifferently, the hardware of the user device 102(3) is used to implementthe functionality of monitoring and controlling incoming and outgoingnetwork 150 traffic based on predetermined security rules. The userdevice 102(3) provisioned to implement the functionality of a firewallestablishes a security barrier between the local network group 150 andany other network, such as the Internet 128 via the mobile trafficnetwork 120. In various embodiments, the user device 102(3) provisionedto implement the functionality of a firewall does not just look at themetadata of communication received from other user devices in the localnetwork group 150; rather, it may also look at the actual datatransported. Based on an internal rule set provided during theprovisioning of the user device to implement the functionality of afirewall, the user device is configured to comprehend how differentcommunication protocols, such as FTP, HTTP, etc., work and can thereforeidentify if a data packet is valid for that particular protocol. If thedata packet is not valid, it can be dropped by the provisioned firewall.

In one embodiment, the user device 102(3) provisioned to implement thefunctionality of a firewall performs stateful inspection of each datapacket. For example, instead of or in addition to examining the contentsof each data packet, key parts of the data packet are compared to adatabase of trusted information, which may be part of the internal ruleset mentioned above. Data packets traveling from the provisionedfirewall to the outside is monitored for predetermined characteristics.Only data packets that match a known active connection are allowed topass the firewall and the rest discarded.

In one embodiment, instead of using a separate communication channelbetween each user device and the base station 104(N), a singlecommunication channel between the local network group 150 (i.e., via theused device 102(3) provisioned as a firewall) can accommodate the manyuser devices 102(3) to 102(N) in the local network group 150. In oneembodiment, the user device that is provisioned to act as a firewall(e.g., 102(3)) also performs the function of a firewall for the sameuser device 102(3). The criteria and process for identifying one or moreuser devices to be provisioned as a switch are discussed in more detaillater.

The security engine 140 of the central server 130 may also instruct theremaining user devices (e.g., 102(4) to 104(7)) to communicate over ashort range technology with the provisioned firewall (e.g., user device102(3). For example, instead of establishing a communication channeldirectly with a base station 104(N), each of the remaining user devices102(4) to 102(7) communicates via short range technology with the userdevice 102(3) that is provisioned as a firewall. In this way, a singlecommunication channel may suffice for all user devices 102(3) to 102(7)in the local network group to provide communication over the mobiletraffic network 120.

In one embodiment, not all user devices in the local network group 150need to subscribe to the mobile traffic network 120. For example, one ormore devices in the local network group 150 may be part of other mobiletraffic network(s)—not shown. However, these user devices may stillsubscribe to the firewall security services discussed herein.

In one embodiment, there is customer relationship management (CRM)server 132 that offers its account holders (e.g., a user of a UD)on-line access to a variety of functions related to the account holders'account, such as on-line payment information, subscription changes,password control, and the like. The CRM may identify whether a userdevice associated with an account of a user is subscribed to the dynamicprovisioning of a firewall role discussed herein. The CRM server 132 mayprovide the user an interface via the Internet 128 to access the accountinformation. Hence, a user's terminal, such as personal computer (PC),may be used to access on-line information about an account of a UD,which the carrier of the mobile traffic network 120 makes available viathe carrier's web site, accessible through the Internet 128. In variousembodiments, the CRM 132 identifies which user device is responsible fora communication using the mobile traffic network 120 via the provisionedfirewall, such that the provisioned firewall is not charged for a routedcommunication. In one embodiment, the functionality of the CRM server132 may be created on the core network via the HSS 108 and PCRF 114,along with a billing server.

For example, if user device 102(6) uses the mobile traffic network 120,it may communicate using short range wireless communication technologywith the user device 102(3), which is provisioned as a firewall. Theuser device 102(3) may provide its own identification information andthat of user device 102(6) to the mobile traffic network 120, such thatthe CRM 132 can bill the appropriate user device for the communication.In one embodiment, the CRM 132 offers bonuses to accounts of userdevices that are provisioned as firewalls.

Accordingly, by virtue of using the dynamic provisioning of the firewallfunction described herein, the security of the communication of the userdevices in a local network group 150 is improved. Further, the networkcongestion with respect to the base station 104(N) may be reduced.Further, power consumption for the user devices participating in thissecurity service may be reduced because communication via short rangewireless communication typically uses a fraction of the power consumedvia a direct channel to the base station 104(N) of the mobile trufflenetwork 120. Accordingly, the security and quality of the serviceprovided to subscribed user devices is improved while the mobilecommunication network provider does not have to make a substantialhardware investment; rather, the resources of subscribed user devicesare used to provide the additional security discussed herein.

While the central server 130 and the CRM server 132 are illustrated byway of example as separate servers, they may be implemented on varioushardware platform combinations. Thus, the functionality described hereinwith respect to each of the servers 130 and 132 can also be provided byone or multiple different computing devices. In other words, the centralserver 130 and the CRM 132 need not be a standalone computing devicesbut can be combined in various configurations. In one embodiment, thecentral server 130 and/or the CRM server 132 may have a scalable andfault-tolerant architecture, such as that provided by a cloud.

Example User Device Components

As discussed in the context of FIG. 1, the dynamic provisioning offirewall role discussed herein involves an interaction withappropriately configured user devices. To that end, it may be useful toconsider the functional elements/aspects of an exemplary user device, ata high-level. For purposes of such a discussion, FIG. 2 provides a blockdiagram illustration of an exemplary user device 200. It will beunderstood that the user device 200 may be a handset type mobile phoneor may be incorporated into another device, such as a personal digitalassistant (PDA), a tablet computer, an IoT device, or the like. Fordiscussion purposes, the illustration shows the user device 200 in theform of a handheld smart-phone.

The user device 200 may include one or more antennae 202, a cellulartransceiver 204, one or more short range wireless communicationtransceiver(s) 205, user interface 206, one or more processors 208,hardware 210, and memory 216. In some embodiments, the antennae 202include an uplink antenna that sends radio signals to a base station,sometimes referred to herein as an eNodeB or base station (e.g., 104(1)in FIG. 1), and a downlink antenna that receives radio signals from theradio tower. In other embodiments, a single antenna may both send andreceive radio signals. These signals may be processed by the cellulartransceiver 204, which is configured to receive and transmit digitaldata. The one or more short range wireless communication transceivers205 may support various short range wireless communication technologies,such as WLAN, WPAN, WSAN, etc. The cellular transceiver 204 and shortrange communication transceiver 205 provide communication ports to theuser device 200.

The user device 200 may include a user interface 206 that enables a userto provide input and receive output from the user device 200. Forexample, the user interface 206 may include a data output device (e.g.,visual display 214, audio speakers, haptic device, etc.,) that may beused to display whether a user device is being provisioned as afirewall, is part of a local network group for security purposes, or isoperated in normal mode (e.g., outside a dynamic provisioning function).The user interface 206 may also include one or more data input devices.The data input devices may include, but are not limited to, combinationsof one or more of keypads, keyboards, mouse devices, touch screens,microphones, speech recognition packages, and any other suitable devicesor other electronic/software selection interfaces that may be used tocommunicate over the mobile traffic network 120.

The user device 200 may include one or more processors 208, which may bea single-core processor, a multi-core processor, a complex instructionset computing (CISC) processor, or another type of processor. Thehardware may include a power source and digital signal processors(DSPs), which may include single-core or multiple-core processors. Theprocessors may perform operation in parallel to process a stream of datathat may be provided over the mobile traffic network 120.

The hardware 210 may also include network processors that manage highspeed communication interfaces, including communication interfaces thatinteract with peripheral components. The network processors and theperipheral components may be linked by switching fabric. The hardwaremay further include hardware decoders and encoders, a network interfacecontroller, and/or a universal serial bus (USB) controller. The networkinterface controller may enable the processors to transmit and receivedata via the mobile traffic network 120 of FIG. 1. In some embodiments,the hardware may also include a direct memory access (DMA) engine. TheDMA engine may enable the various controllers to access the memory 216independently of the one or more processors 208 to perform tasks. Thevarious controllers and processors of the user device 200 may executeinstructions and perform tasks under the direction of softwarecomponents that are stored in the memory 216.

The memory 216 may be implemented using computer-readable media, such ascomputer storage media. Storage media includes volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules, orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD), high definition video storage disks, or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other non-transmissionmedium that can be used to store information for access by a computingdevice.

The memory 216 may store various software components that are executableor accessible by the processor(s) 208 and controller(s) of the userdevice 200. The various components of the memory 216 may includesoftware 218, rule set 222, and an operating system 224. Each softwaremodule may include routines, program instructions, objects, and/or datastructures that perform particular tasks or implement particularabstract data types. For example, the software 218 of the memory 216 mayinclude a self-monitoring application 220 that is operative to receiveand follow instructions from the security engine 140 of the centralserver 130 of FIG. 1. These instructions may include for the user device200 to be provisioned as a firewall for a local network group of userdevices 150, to protect user devices in a local network group 150 fromtraffic with other networks over the mobile traffic network 120, and/orto solicit a status report for the security engine 140.

Accordingly, the self-monitoring application 220 is configured toevaluate various parameters of the corresponding user device 200 toprovide these parameters of the user device 200 to the security engine140. From this status information, sometimes referred to herein as astatus report, the security engine 140 of the central server 130 canidentify a device security posture for the user device, discussed inmore detail later.

The self-monitoring application 220 may provide various indicia ofvulnerability. Typically, indicia include connectivity to untrustedand/or unauthenticated network locations, transfer of data fromuntrusted and/or unauthenticated sources, and data access by untrustedand/or unauthenticated applications. For example, the self-monitoringapplication 220 may determine the type of applications presently runningon the user device 200. It may also determine the type of communicationpresently occurring over its ports (via its cellular transceiver 204and/or short range communication transceiver 205). Such communicationmay be, without limitation, via a User Datagram Protocol (UDP), FileTransfer Protocol (FTP), Secure FTP (FTPS), Transport Layer Security(TLS), Secure Sockets Layer (SSL), Pretty Good Privacy (PGP), HypertextTransfer Protocol (HTTP), Secure HTTP (HTTPS), etc. The self-monitoringapplication 220 may also include the addresses that the user device ispresently in communication with. Such addresses may include, withoutlimitation, an IP address and a hardware address (e.g., in the form of aMedia Access Control (MAC) address). In one embodiment, theself-monitoring application 220 may determine the presence of securityagents, such as anti-virus or a personal firewall, in its indicia ofvulnerability for the user device 200.

The self-monitoring application 220 may identify its computing capacity.For example, the self-monitoring application 220 may determine theavailable processing power and the processing load of the processors)208. In one embodiment, even if the user device 200 has a large inherentprocessing power, a low available processing capability may be reportedif there are many processes presently running that are slowing down theuser device 200. Similarly, other parameters, such as the availablememory 216, signal strength of the cellular transceiver 204 (and/or theshort range wireless communication transceivers) 205), and the presentpower supply situation are identified. For example, the user device 200may be running off a battery in the hardware 210. In this regard, theavailable percentage of battery power remaining may be identified. Ifthe user device 200 is connected to an uninterrupted power supply, thenthis information may be included in the status report.

The self-monitoring application 220 may also determine what other userdevices are in a short range wireless communication technology range. Tothat end, the self-monitoring application of each participating userdevice may cooperate to provide their identification information andsignal strength. The identification information may include theinternational mobile station equipment identity (IMEI), mobileidentification number (MIN), mobile equipment identifier (MEID), or thelike.

In various embodiments, the foregoing parameters, including the indiciaof vulnerability and computing capacity, together with theidentification information of the user device 220 (and other userdevices the present user device 220 is in scope of short range wirelesscommunication with) are reported to the security engine 140 of thecentral server 130 by the self-monitoring application 220 in a statusdata packet. The status data packet may be provided at predeterminedintervals, upon a trigger event, or upon request from the centralserver.

A trigger event may be a change in status of the user device, such as areduction in available processing power due to a larger load on theprocessor(s) 208, dropping below a predetermined power threshold (e.g.,20%), being out of range from a present base station or from the localnetwork group 150, to initiate a handover, etc. A trigger event may alsoinclude a change in an indicia of vulnerability.

Upon receipt of the status data packet, the security engine 140identifies a device security posture (related to a security risk of theuser device 200) and assigns a competence score to the user device 200(regarding its capability of being provisioned as a firewall). Thenotion of a competence score is discussed in more detail later.

The rule set 222 may include network security rules that are provided tothe user device 200 via the security engine 140 of the central server130 during the provisioning of the user device 200 to perform thefunctions of a firewall. In various scenarios, the rule set 222 may bebased on the security risk perceived by the security engine 140.

The operating system 224 may include components that enable the userdevice 200 to receive and transmit data via, various interfaces usercontrols, communication interface, and/or memory input/output devices),as well as process data using the processors 204 to generate output. Theoperating system 224 may include a presentation component that presentsthe output (e.g., display the data on an electronic display 214 of theuser device 200, store the data in memory 216, transmit the data toanother user device (e.g., via a short range wireless communicationtechnology), etc.). Additionally, the operating system 224 may includeother components that perform various additional functions generallyassociated with an operating system.

Example Use Case

With the foregoing overview of an example architecture for implementinga wireless network optimization system of FIG. 1 and a block diagramillustration of an exemplary user device of FIG. 2, it may be helpful toprovide an example use case. To that end, FIG. 3 illustrates an examplescenario where user devices are dynamically provisioned the role of afirewall. Consider, for example, a concert at an arena or a large officebuilding with multiple floors. There may be many user devices(represented by user devices 302(1) to 302(1)) that are configured tocommunicate over one or more mobile traffic networks, such as mobiletraffic network 120. Thus, many user devices in a common geolocation maybe using the resources of the mobile traffic network 120. Some of thecommunication may be subject or vulnerable to malicious activity, suchas Botnet, distributed denial of service (DDOS), Malware, and the like,collectively referred to herein as a security concern.

Consider now that each of the user devices 302(1) to 302(10) depicted insystem 300 is subscribed to the dynamic provisioning security servicediscussed herein. To that end, each of the user devices 302(1) to302(10) has a self-monitoring application stored in its memory that isconfigured to identify its indicia of vulnerability and computingcapacity in the form of a status report to the central server 130 overthe mobile traffic network 120 at predetermined intervals, upon request,or upon a trigger event. The computing capacity of the correspondinguser device, comprising the following parameters: (i) an availableprocessing power of the user device; (ii) an available memory of theuser device; (iii) a signal strength to the base station (e.g., to themobile traffic network 120) of the user device; (iv) an available supplypower of the user device; and (v) a short range technology capability ofthe user device. Upon receipt of the status report, the security engine140 of the central server 130 may assign a score to each parameter abovebased on a magnitude of each parameter, respectively.

For example, a user device with more available processing power receivesa higher score than one that has a slower CPU, has fewer CPU cores, oris identified to be slowed down by multiple processes. Similarly, a unitwith more available memory receives a higher score than one that hasless available memory. For each user device 302(1) to 302(10), a totalscore, referred to herein as a competence score, is calculated by thesecurity engine 140 by summing the scores of all parameters for eachuser device, respectively. In one embodiment, each parameter is weightedbased on the significance of the parameter. Thus, the sum reflects aweighted total score. These status reports and scores may be stored in amemory of the central server 130.

The security engine 140 of the central server 130, is configured toprovide various functions for the scenario 300. Its functions include,without limitation, (i) soliciting and receiving the status reports inthe form of status data packets from the self-monitoring application ofeach user device participating in the security service discussed herein,(ii) determining a network posture, (iii) determining a device securityposture (e.g., for each user device), (iv) provisioning one or more userdevices to perform the function of a firewall, (v) and orchestrating ahandover function of the role of the firewall to another one or moreuser devices.

The security engine 140 of the central server 130 may determine whetherone or more user devices are subject to a security risk. To that end,the security engine 140 identifies the user device security posturebased on the indicia of vulnerability provided by the same user device.In one embodiment, the security posture of a user device is also basedon the network posture.

The network 120 posture may be determined by the security engine 140 viaone or more network analyzers in the mobile traffic network 120. Eachnetwork analyzer intercepts and logs traffic that passes over the mobiletraffic network 120 or part thereof. It acts as a “sniffer” to captureeach data packet and may decode the packet's raw data to identify thevalues of various fields in the packet to identify any security threatstherein.

The security engine 140 evaluates indicia of vulnerability (and, in oneembodiment, the network posture) in view of a security rule set 370stored in a memory of the central server to identify the device securityposture for each user device. The security rule set 370 includescriteria (e.g., triggers) that are used to determine a potentialsecurity risk for a user device. As discussed previously, the userdevice security posture may be based on the type of applicationspresently running on the device, the type of communication presentlyoccurring over its ports, and the addresses that the user device ispresently in communication with, whether communication is with untrustedor unauthenticated network locations and/or applications, the presenceof security agents. In one embodiment, if a security agent alreadyexists for a user device, it is deemed to be secure. However, it maystill be used to be provisioned as a firewall for its local networkgroup.

For example, the more open communication ports are available, the morevulnerable the user device may be. Further, some applications may bedeemed by the security rule set 370 to be riskier than others.Similarly, some type of communication is more secure than others. Forexample, FTPS is more secure than FTP; SSL is more secure than TLS;HTTPS is more secure than HTTP; etc. The security rule set 370 may alsoinclude a reference table of addresses that are deemed to pose asecurity risk. In various embodiments, the security rule set 370 may becategorical (e.g., if a certain condition exists, then it is a securityrisk) or cumulative (e.g., the vulnerabilities are tabulated inaggregate and if they are above a predetermined threshold, as defined inthe security rule set 370, then the user device is deemed to have asecurity risk).

Upon determining that there is a concentration of user devices at acoverage area (e.g., a geolocation having a predetermined range, such asthe concert hall), the security engine 140 of the central server 130 maycreate one or more separate local network groups (i.e., groups 350 and360 in the example of FIG. 3), based on the user devices that are withina scope of short range wireless communication of each other. In oneembodiment, it is not necessary for a user device to have a devicesecurity posture that is considered a security risk. Rather, simplybeing within a short range wireless communication range of otherparticipating user devices is enough to be included in the local networkgroup. Each of these local network groups 350 and 360 may be used toprovide additional security to the corresponding local network group inparticular, and the mobile traffic network 120 in general.

In one embodiment, if a user device may qualify (e.g., 302(5)) to be ineither local network group 350 or 360 due to being able to communicatein short range wireless communication technology with both local networkgroups 350 and 360, in various embodiments, such user device (e.g.,302(5)) is included in the group based on (i) proximity (e.g., via UPScoordinates or base station triangulation) to the other user devices, or(ii) load leveling the number of user devices associated with aprovisioned firewall.

The security engine 140 may select one of the plurality of user devices102(3) to 102(7) that has the highest competence score in its localnetwork group (e.g., user device 302(1) in local network group 350, anduser device 302(6) in local network group 360) to act as a firewall forits respective local network group. In this regard, the security enginemay provision the user device 302(1) to act as a firewall for the firstlocal network group 350 and provision the user device 302(6) to act as afirewall for the second local network group 360.

For example, a message may be sent to the self-monitoring application ofthe user device 302(1) to perform a virtualized network function (VNF)of the firewall for the first local network group 350. Thus, networkfunctions may be implemented in a virtualized manner on the user device302(1), which is used as a commodity computing hardware. Putdifferently, the function of the firewall functionality is attributed toa selected user device (i.e., 302(1)). Similar action is performed onuser device 302(6) for the second local network group 360.

In one embodiment, for each local network group 350 and 360, theremaining user devices (i.e., 302(2) to 302(5) for local network group350, and 302(7) to 302(10) for local network group 360) are instructedby the security engine 140 to route communication through the selecteduser device (202(1) and 302(6), respectively) via a short range wirelesscommunication technology.

Consider now that the user device 302(7) is moved from one area toanother. In this regard, the self-monitoring app of the user device302(7) sends a notification to the security engine 140, which may be inthe form of a status report, discussed previously. Upon determining thatthe user device 302(7) is now in scope of short range wirelesscommunication to the first local network group 350, the user device302(7) is assigned to the first local network group 350. Accordingly,traffic from the user device 302(7) may continue via the virtualfirewall performed by user device 302(1).

In one scenario, user device 302(6), which has been provisioned in thisexample as a firewall for the second local network group 360, mayexperience a trigger event. For example, user device 302(6) may move outof scope of short range wireless communication from one or more userdevices 302(7) to 302(10), have a reduction in available processingpower, go below a predetermined battery power threshold (e.g., 20%),etc., collectively referred to herein as a failure of the provisioneduser device. Upon the security engine 140 learning of the new status(i.e., failure) of the user device 302(6) from the self-monitoringapplication of the user device 302(6), the security engine 140 mayperform a handover operation by provisioning the functionality of thefirewall to another user device that has the present highest competencescore in the local network group (i.e., second local network group 360in this example).

Example Call Flow Process

With the foregoing overview of the mobile communication network 100, thevarious components of an example user device 200, and the example usecase 300, it may be helpful now to consider a high-level discussion ofan example call flow process. To that end, FIG. 4 presents anillustrative process 400 for dynamically provisioning a firewallfunction to a user device. The process 400 is illustrated as a logicalflow, winch represents a sequence of operations that can be implementedin hardware, software, or a combination thereof. In the context ofsoftware, the blocks represent computer-executable instructions that,when executed by one or more processors, perform the recited operations.Generally, computer-executable instructions may include routines,programs, objects, components, data structures, and the like thatperform particular functions or implement particular abstract datatypes. The order in which the operations are described is not intendedto be construed as a limitation, and any number of the described blockscan be combined in any order and/or in parallel to implement theprocess. For discussion purposes, the process 400 is described withreference to the architecture of the mobile communication network 100 ofFIG. 1 and the user device of FIG. 2.

At block 402, the security engine 140 receives status reports from userdevices at a coverage area. As discussed previously, in variousembodiments, a self-monitoring application of each user device thatparticipates in the firewall provisioning service discussed herein maysend (i) various indicia of vulnerability, (ii) its present computingcapacity, and (iii) identification information (i.e., of self and otheruser devices it is capable of having short range wireless communicationwith) to the security engine 140, as a status report in the form of adata packet. Such status report may be received at predeterminedintervals, upon a trigger event, or upon request from the securityengine 140. In the example of process 400, it is assumed that the statusreport is requested by the security engine 140.

At block 404, the security engine 140 of the central server 130determines the security posture of user devices for the coverage area.In one embodiment, the security engine 140 also monitors the networkposture, and the device security posture includes aspects of the networkposture. In various embodiments, each coverage area may be associatedwith a particular base station (e.g., 104(1) to 104(N)) or there may beseveral geo-locations for a particular base station.

At block 406, the security engine 140 determines whether there is asecurity concern for one or more user devices at a coverage area basedon their determined device security posture. Upon determining that thereis no security concern for the user devices at a coverage area (i.e.,“NO” at decision block 406), the process continues with the monitoringmode of block 402. However, upon determining that there is a securityconcern (i.e., “YES” at decision block 406), the process continues withblock 408.

At block 408, the security engine 140 creates a local network group ofuser devices based on the user devices that are within a scope of shortrange wireless communication of each other, (e.g., 102(3) to 102(7)).

At block 410, the security engine 140 selects a user device (e.g.,102(3)) from the plurality of user devices 102(3) to 102(7) that has thehighest competence score in its local network to implement thefunctionality of a firewall. In some embodiments, if the number of userdevices in the local network group is above a predetermined threshold,then additional user devices (i.e., ones having the highest competencescore(s)) are selected to implement the function of the firewall. Putdifferently, multiple user devices may be provisioned to implement thefunctionality of a firewall for a local network group.

At block 412, the security engine 140 provisions the user device 102(3)to act as a firewall for the local network group 150. To that end, amessage is sent to the self-monitoring application of the user device102(3) to perform a VNF of a firewall for the local network group 150.

At block 414, the security engine 140 instructs the user devices in thelocal network group 150 to (e.g., instead of using a cellulartransceiver to communicate over the mobile traffic network 120) routeall communication via a short range wireless communication technology tothe provisioned firewall. In various embodiments, this instruction maybe received by each user device 102(3) to 102(7) in the local networkgroup 150 directly via a direct connection between a base station (e.g.,104(N)) and the corresponding user device or relayed by the firewallprovisioned user device 102(3) to the remaining user devices (102(4) to102(7)) via short range wireless communication.

Consequently, at block 416, all communication of the local network group150 is routed through the selected user device 102(3), which performsthe functionality of a firewall for the local network group 150.

User devices :102(3) to 102(7) of the local network group 150 may changetheir status over time. In this regard, at block 418, the securityengine evaluates whether a trigger event occurs. For example, userdevice 102(3), which has been provisioned as a firewall, may move out ofscope of short range wireless communication from one or more userdevices in the local network group 150, or have a reduction in availableprocessing power, go below a predetermined battery power threshold(e.g., 20%). Further, a user of the user device 102(3) may turn OFF thedynamic provisioning feature. Upon the security engine 140 learning ofthe new status of the user device 102(3) from the self-monitoringapplication of the user device 102(3) or not receiving communicationfrom the user device 102(3) for a predetermined period (i.e., “YES” atdecision block 418), the security engine 140 may continue with block402, which may ultimately lead to a handover operation. However, ifthere is no trigger event (i.e., “NO” at decision block 418), theprocess continues with block 416, where communication continues to berouted through the selected user device 102(3), which is provisioned asa firewall.

Example Computer Platform

As discussed above, functions relating to providing a dynamicprovisioning of a firewall to user devices over a wireless network canbe performed on one or more computing devices connected for datacommunication, as shown in FIG. 1 and in accordance with the exampleprocess 400 of FIG. 4. An exemplary computing device in the form of auser device 102 has been discussed above with respect to FIG. 2. FIG. 5provides a functional block diagram illustration of a computer hardwareplatform. In particular, FIG. 5 illustrates a network or host computerplatform 500, as may be used to implement a server, such as the centralserver 130.

A computer configured as a server, for example, includes a datacommunication interface 506 for packet data communication. The servercomputer may include an I/O interface 516 that may include a display, atouch screen, a keyboard, a pointing device, a microphone, aloudspeaker, and/or any other type of user interface device. The servercomputer also includes a central processing unit (CPU) 502, in the formof one or more processors, for executing program instructions. Theserver platform may include an internal communication bus 504, programstorage 508, and data storage for various data files to be processedand/or communicated by the server, although the server may receiveprogramming and data via network communications. Data can be stored invarious forms of computer-readable media, including (but not limited to)hard disk 508, random access memory (RAM) 510, read only memory (ROM)512, and the like. The central server has a security engine 509 storedin its memory, represented by way of example only and not limitation, ashard disk 508.

The hardware elements, operating systems and programming languages ofsuch servers are conventional in nature. In one embodiment, the serverfunctions may be implemented in a distributed fashion on a number ofsimilar platforms, to distribute the processing load. In one embodiment,the functionality of the server discussed herein may be combined in oneor more server platforms. For example, the functions of the CRM 132 andthe central server 130 may be performed on the same server centralserver 130). In one embodiment, the platform 500 may have a scalable andfault-tolerant architecture, such as that provided by the cloud.

The software functionalities discussed herein involve programming,including executable code as well as associated stored data, e.g., filesused for applications on the central server 130, such as the securityengine 140, as discussed herein. In one embodiment, there may be asecurity rule-set 370 to help identify the device security posture foreach user device.

The software code is executable by the corresponding computing device.In operation, the code is stored within the computing device. At othertimes, however, the software may be stored at other locations and/ortransported for loading into the appropriate computing device system.Execution of such code by a processor of the computing device enablesthe computing device to perform the provisioning of the functionality ofthe firewall function to a user device described herein. Hence, aspectsof the methods of improving the security over the mobile traffic networkas outlined above may be embodied in programming. Program aspects of thetechnology may be thought of as “products” or “articles of manufacture”typically in the form of executable code and/or associated data that iscarried on or embodied in a type of non-transitory machine readablemedium.

CONCLUSION

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended by the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

It is understood that the dynamic provisioning of a firewallfunctionality on a user device is performed upon subscriber approval.

It is understood that any specific order or hierarchy if steps in theprocess disclosed in FIG. 4 are illustrations of exemplary approaches.Based upon design preferences, it is understood that the specific orderor hierarchy of steps in the processes may be rearranged, expanded, andsome steps omitted. Some of the blocks may be performed simultaneously.For example, the action of receiving status reports from user devices ina coverage area may be performed continuously, at predeterminedintervals, upon request from the security engine 140, or upon a triggerevent.

Unless otherwise stated, all measurements, values, ratings, positions,magnitudes, sizes, and other specifications that are set forth in thisspecification, including in the claims that follow, are approximate, notexact. They are intended to have a reasonable range that is consistentwith the functions to which they relate and with what is customary inthe art to which they pertain.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”or any other variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises a list of elements does not include only those elements butmay include other elements not expressly listed or inherent to suchprocess, method, article, or apparatus. An element proceeded by “a” or“an” does not, without further constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises the element.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter. _cm What isclaimed is:

1. A computing device configured to provide a security service to amobile traffic network, the computing device comprising: a processor; anetwork interface communicatively coupled to the processor andconfigured to enable communications with the mobile traffic network; astorage device for content and programming; a security applicationstored in the storage device, wherein execution of the securityapplication by the processor configures the computing device to performacts comprising: creating a local network group comprising a pluralityof user devices that are subscribed to the security service; selectingone of the plurality of the user devices to act as a firewall for theplurality of user devices of the local network group; provisioning theselected user device to act as a firewall for the local network group;and sending a message to the plurality of user devices of the localnetwork group to route communication through the selected user devicevia a short range wireless communication technology.
 2. The computingdevice of claim 1, wherein creating the local network group is inresponse to: receiving from each user device at a coverage area a statusreport, wherein the status report of each user device comprises: indiciaof vulnerability of the user device; a present computing capacity of theuser device; and an identification information of the user device andother user devices in communication range with the user device;determining, for each user device, a security posture of the subscribeduser device based on the indicia of vulnerability; and identifying thatat least one of the user devices at the coverage area has a securityrisk based on the security posture.
 3. The computing device of claim 1,wherein the selection of the user device to act as a firewall is basedon: receiving, from each user device of the local network group, astatus report including a present computing capacity of the user device,from a self-monitoring application of the user device, respectively;determining, for each user device of the local network group, acompetence score based on its present computing capacity; and selectinga user device of the local network group based on the competence score.4. The computing device of claim 3, wherein the present computingcapacity of each user device in the local network group is based on thefollowing parameters: a short range technology capability; an availableprocessing power of the user device; an available memory of the userdevice; a signal strength to a base station of the mobile trafficnetwork; and an available supply power of the user device.
 5. Thecomputing device of claim 4, wherein execution of the securityapplication further configures the computing device to perform actscomprising: for each user device in the local network group: assigning ascore to each parameter based on a magnitude of each parameter,respectively; and calculating the competence score by summing theweighted scores of all parameters of the user device.
 6. The computingdevice of claim 3, wherein the provisioning of the selected user deviceto act as a firewall for the local network group comprises: sending amessage to the self-monitoring application of the selected user deviceto perform a virtualized network function (VNF) of the firewall for thelocal network group.
 7. The computing device of claim 1, wherein thecreation of the local network group is based on user devices in acoverage area that are within a short range wireless communicationtechnology range of each other.
 8. The computing device of claim 7,wherein the short range wireless communication technology is based on atleast one of: Digital Enhanced Cordless Telecommunications (DECT), NearField Communication (NFC), ZigBee, Bluetooth, ultra-wideband (UWB), andwireless USB.
 9. The computing device of claim 1, wherein execution ofthe security application further configures the computing device toperform acts comprising: upon determining that a single user devicecannot accommodate all the user devices in the local network group,selecting a second user device in the local network group to support theselected user device such that both user devices act as a firewall forthe local network group.
 10. The computing device of claim whereinexecution of the security application further configures the computingdevice to perform acts comprising: upon determining that a user deviceof the local network group has moved from one coverage area to anotherand is in a scope of short range wireless communication to a secondnetwork group, assigning the user device to the second network group.11. The computing device of claim 1, wherein execution of the securityapplication further configures the computing device to perform actscomprising: upon determining of a failure of the provisioned selecteduser device, selecting and provisioning another user device to act as afirewall.
 12. The computing device of claim 1, wherein the act ofsending the message to the plurality of user devices of the localnetwork group to route communication through the selected user devicevia the short range wireless communication technology comprises: sendingthe message to the selected user device via a cellular connection usingthe network interface between the mobile traffic network and theselected user device; and relaying the message to a remaining userdevices in the local network group by the selected user device via theshort range wireless communication technology.
 13. The computing deviceof claim 1, wherein the provisioned user device is an internet of things(IoT) device.
 14. A non-transitory computer-readable medium havingstored thereon a plurality of sequences of instructions which, whenexecuted by a processor, cause the processor to perform a method ofproviding security service to a mobile traffic network, the methodcomprising: creating a local network group comprising a plurality ofuser devices that are subscribed to the security service; selecting oneof the plurality of the user devices to act as a firewall for theplurality of user devices of the local network group; provisioning theselected user device to act as a firewall for the local network group;and sending a message to the plurality of user devices of the localnetwork group to route communication through the selected user devicevia a short range wireless communication technology.
 15. The method ofclaim wherein creating the local network group is in response to:receiving from each user device at a coverage area a status report,wherein the status report of each user device comprises: indicia ofvulnerability of the user device; a present computing capacity of theuser device; and an identification information of the user device andother user devices in communication with the user device; determining,for each user device, a security posture of the subscribed user devicebased on the indicia of vulnerability; and identifying that at least oneof the user devices at the coverage area has a security risk based onthe security posture.
 16. The method of claim 14, wherein the selectionof the user device to act as a firewall is based on: receiving, fromeach user device of the local network group, a status report including apresent computing capacity of the user device, from a self-monitoringapplication of the user device, respectively; determining, for each userdevice of the local network group, a competence score based on itspresent computing capacity; and selecting a user device of the localnetwork group based on the competence score, wherein the presentcomputing capacity of each user device in the local network group isbased on the following parameters: an available processing power of theuser device; an available memory of the user device; a signal strengthto a base station of the mobile traffic network; and an available supplypower of the user device.
 17. The method of claim 16, wherein theprovisioning of the selected user device to act as a firewall for thelocal network group comprises: sending a provisioning message to theself-monitoring application of the selected user device to perform avirtualized network function (VNF) of the firewall for the local networkgroup.
 18. The method of claim 14, wherein sending the message to theplurality of user devices of the local network group to routecommunication through the selected user device via the short rangewireless communication technology comprises: sending the message to theselected user device via a cellular connection between the mobiletraffic network and the selected user device; and relaying the messageto a remaining user devices in the local network group by the selecteduser device via the short range wireless communication technology.
 19. Acomputing device, comprising: a processor; a network interfacecommunicatively coupled to the processor and configured to enablecommunications with the mobile traffic network; a storage device forcontent and programming; a self-monitoring application stored in thestorage device, wherein execution of the self-monitoring application bythe processor configures the computing device to perform actscomprising: creating a status report of the user device including:indicia of vulnerability of the user device; a present computingcapacity of the user device; and an identification information of theuser device and other user devices in communication with the userdevice; sending the status report via the network interface over themobile traffic network to a central server; and receiving an instructionfrom the central server to be provisioned as a firewall to a pluralityof user devices in a local network group.
 20. The computing device ofclaim 19, wherein execution of the self-monitoring application by theprocessor further configures the computing device to perform actscomprising: sending a message to the plurality of user devices of thelocal network group to route communication through the selected userdevice via a short range wireless communication technology.